Clarify WebTransport datagram writable support#44317
Conversation
|
@KirtiRamchandani As discussed, it's best not to fix issues that still have the "needs-triage" label - they might not be correct, and even if they are true, the proposed solution might not be optimal. I've suggested a solution in in #44273 (comment) |
|
Thanks, updated in
Local checks:
|
|
Preview URLs (2 pages) Flaws (4) Found an unexpected or unresolvable flaw? Please report it here. URL:
URL:
(comment last updated: 2026-06-09 06:36:50) |
7acd1bc to
49119c3
Compare
docs: update WebTransport datagram writable example
49119c3 to
fcf7d62
Compare
|
I've created #44383 that this can go in after. Note, I also modified the text slightly. This was merged into your commit accidentally, so it ias attributed to you. I decided not to use a note to highlight the differences between the method and property. Anyway, I'll look at this again after #44383 goes in. |
Description
Adds explicit deprecated/non-standard markers and compatibility notes beside the WebTransport datagram examples that use
WebTransportDatagramDuplexStream.writable.Motivation
The
WebTransport.datagramspage can show Baseline support for thedatagramsproperty while the outgoing datagram example useswritable, which has separate compatibility data, is deprecated, is non-standard, and is not supported in Safari. The added notes make that distinction visible where readers encounter the example.Additional details
The same outgoing datagram example appears on the
WebTransportDatagramDuplexStreamoverview, so this updates both pages consistently.Related issues and pull requests
Fixes #44273
Tests
git diff --check -- files/en-us/web/api/webtransport/datagrams/index.md files/en-us/web/api/webtransportdatagramduplexstream/index.md